This document describes activities to check SAP HANA financial reporting model's correctness and completeness. It summarizes business process activities in a logical sequence The scenario includes the following process steps:
The target groups for this document are SAP customers and consultants with little knowledge of the SAP Bank Analyzer, SAP HANA, and SAP Business Objects reporting concept and features. Content target groups for this scenario are banks and financial institutes, particularly the departments within these, which are enabled to do faster-reporting processing on a daily and ad hoc sub-ledger reporting.
Master Data and Organizational Data
The preparation of the master data is not necessary. The master data is created directly in the SAP Bank Analyzer system. For an example of how to maintain the master and flow data of a financial product, see the appendix of this document.
Business Conditions
In this case, the business conditions are maintained on the financial product in the SAP Bank Analyzer. For an example of how to maintain the financial conditions, see the appendix of this document.
Roles
Business roles are not included in the delivery of the solution. However, the following process is modelled for particular users.
User | Description |
Banker | The bank clerk who creates financial transactions in the SAP Bank Analyzer and who analyzes the financial reporting afterwards |
Technical Expert | The technical expert verifies the proper replication of newly created data in the |
User | Description |
(Optional) | SAP HANA Studio (this role is optional). See the Appendix of this document |
The following summary describes the relevant process steps: Process step Business Business Role Expected Results Condition Create Financial Customer request Banker New Financial Transaction with Transaction/Financial business transactions are instrument with created and posted / RDL business Postings transactions Financial Reporting --- Banker Financial Reporting results Analysis via SBO Crystal Reports and/or SBO Explorer Verify data in SAP --- Technical Expert The postings are replicated and HANA (optional) available in SAP HANA
Create a Financial Product
Use In this activity, you create a financial product in the SAP Bank Analyzer.
Prerequisites
Make sure that the user has access and the necessary authorizations to create financial products in the SAP Bank Analyzer.
If you want to enrich your career and become a professional in SAP Hana, then visit Tekslate - a global online training platform: "SAP Hana Administration Training" This course will help you to achieve excellence in this domain. |
Procedure
Log on to the SAP Bank Analyzer system via the SAP logon: <System name>; <Client>, <Username>, <Logon language>;
To create an account, access the transaction using one of the following navigation options
SAP Menu | Financial Services Bank Analyzer Source Data LayerPrimary Object Account Create Account |
Transaction Code | /BA1/F1_ACC_01 |
To create financial produce, access the transaction using one of the following navigation options:
SAP Menu | Financial Services Bank Analyzer Source Data LayerPrimary ObjectFinancial transaction Create Financial Transaction/ Financial instrument Create financial Instrument (Please create a financial transaction or financial instrument) |
Transaction Code | /BA1/F1_CF_00_01 (Financial transaction)/BA1/F1_CF_01_01 (Financial instrument) |
Create relevant business transactions for the financial product
Execute the following process steps for the created financial product
Create a Business Transaction |
|
SAP Menu | Financial Services Bank Analyzer Processes and Methods Set SDL timestamp |
Transaction Code | /BA1/B0_CLOSE_SDL |
Aggregation (using the Run Accounting Daily Report for the aggregation) |
|
Note | 1592938 (Applying SAP note) |
Report | ZBA1R_RUN_ACC_DAILY |
ALTERNATIVE | Run the whole Aggregation processes step by step:/BA1/F2_PB_PR, /BA1/FG_PR_FT, /BA1/FG_PR_BT_PRE, /BA1/FG_PR_BT_PRE, /BA1/FG_PR_RABT, /BA1/FG_PR_BT, /BA1/FG_PR_AC_CURR, /BA1/FG_PR_AC_REASS, /BA1/FG_PR_AC_RETRO, /BA1/FG_PR_DERIV_AE |
Post External Business Transaction |
|
SAP Menu | Financial Services Bank Analyzer Processes and Methods Accounting for Financial products Automatic processing Accounting processes Post external business transaction |
Transaction Code | /BA1/B1_PBTP_FDB_SL |
Update Secondary |
|
SAP Menu | Financial Services Bank Analyzer Processes and Methods Accounting for Financial products Automatic processing Accounting processes Update Secondary business transactions |
Transaction Code | /BA1/B1_US_SL |
Verify the postings in the Result – Viewer of the SAP Bank Analyzer.
Result-viewer |
|
SAP Menu | Financial Services Bank Analyzer Result Data Layer Display Result Data |
Transaction Code | /BA1/HW_RESULT VIEWER |
Result
You have created a financial product and executed the relevant SAP Bank Analyzer processes. You have created postings in the Result Data Layer. You can display them via the Result-View.
Financial Reporting Analysis with SAP Business Objects Crystal Reports
This chapter gives an overview of the SAP Business Objects Crystal Report templates. Please note that the whole reporting is based on the sub-ledger postings on SAP Bank Analyzer and does not consider postings for the general ledger.
The balance statement is provided as an SAP Business Objects Crystal Report template (Balance Report). The Balance Report is based on a point in the Calculation. For detailed information regarding the structures and result and result objects of the Balance, Report sees the configuration guide (Appendix).
The profit and loss are provided as SAP Business Objects Crystal Report template (Profit & Loss Report). The Profit & Loss Report is based on a period of time calculation. The income statement considers the balance of income and expenses. It is part of the annual financial statements. For detailed information regarding the structures and result objects of the Profit & Loss Report see the configuration guide (Appendix).
The basic framework is the sub-ledger reporting reconciled balance statement and profit and loss statement. The balance sheet from the accounting sub leger for financial accounting is based on the definitions given by the Committee of European Bank Supervisors within the core section of the framework of the guidelines of financial reporting. The two sub-ledger report templates – Balance Report and Profit & Loss Report – are based on a three-level structure hierarchy that reflects the respective balance sheet positions. The reports provide the option to drill down directly to the G/L account by choosing the relevant balance position in the main report. It is also possible to check the composition of a position, which can contain multicurrency amounts (by choosing the $ amount icon in the main report.) The main reports present the amounts in two different approaches. The first column is based on actual figures in reporting currency in the Result Data Layer. The second column – Ad hoc amount – represents the converted figures from the reporting currency with the current exchange rate. Note that it is a conversation only and not a valuation.
Access to SAP Business objects crystal reports via the BI Launch pat
URL | https://<server>:<port>/BOE/BI |
Input username and password and choose Log on.
On the Documents tab pages, go to the SAP Crystal Reports (for example Documents
Folders
Public Folders
SAP
SAP.FS
SAP.FS.BA).
Crystal Reports are marked as the type Crystal Report.
The adjustment of the Crystal Report templates is described in the configuration guide (chapter SAP Crystal Report Enhancement).
This chapter gives an overview of how to use the SAP Business Objects Explores for exploring data of created information Spaces.
The Creation of Information Spaces is described in the configuration guide (chapter SAP Business Objects information Space Creation).
The following Information Spaces examples are listed in the configuration guide:
The following steps describe the launch of information spaces:
Access SAP business objects Explorer via the BI launchpad:
URL | https://<server>:<prot>BOE/BI |
Input your username and password and choose Log on.
Under My Applications, go to the SBO Explorer.
Scroll through the available information Spaces or use the search function to select the relevant Information Space and start the selected information Space.
An Explore tab page opens. Then you can navigate through the information space.
Example of Master Data and Flow Data
The following table shows an example of how to fill the master data and flow data in the prerequisite section in case of a BOND:
Account – Securities Position Account |
|||||
ENTRANCE SCREEN |
|||||
Template | S43SECPACC | ||||
Template Version | SV1 | ||||
Account Category | Securities Position Account | ||||
External Number | Insert your name for the settlement account | ||||
ACCOUNTING BASIC DATA |
|||||
Business record data | 01.01.2000 | ||||
Authorizations Group | NONE | ||||
Account Status | 00 | Active | |||
Source System | MANUAL | ||||
Organizational Unit | PC11-11 | ||||
ATTRIBUTES |
|||||
Banking/Trading Book | 1 | Banking Book | |||
Legal Entity | Insert your legal entity |
FINANCIAL TRANSACTION – FINANCIAL INSTRUMENT |
|||||
HEADER |
|||||
Template | S41BONDEX | ||||
Template Version | SV1 | ||||
External Number | LEXX DOND 2010 | ||||
Authorization Group | MANUAL | ||||
Business Record Data | 01.01.2010 | ||||
Node Number | 1 | ||||
BASIC DATA |
|||||
Status | 01 | ACTIVE | |||
Source System | MANUELL | ||||
Sales Product | STRABOND | BOND IN TRADING PORTFOLIO | |||
State Date of Obj | 01.01.2010 | End Date of Obj | 31.12.2013 | ||
Start Fixed Inl | 01.01.2010 | End of Fixed inL | 31.12.2013 | ||
Calendar | 01 | Germany (Standard) | |||
Currency | USD | ||||
Customer Rate | 0.000000000 | ||||
Receivable/Liability | 2 | Receivable/Liability | |||
Day Count Conv | 3 | Act/365 | |||
Templ. Variant | SFIC | Financial condition | |||
Class. Risk Basis | |||||
FINANCIAL CONDITIONS |
|||||
Activity Type | STD | Standard | |||
Condition Group Type | 2002 | Securities | |||
Valid From | 01.01.2010 | ||||
End Date | 31/12/2013 | ||||
Tab Calculation | |||||
Condition form | Fixed Condition | ||||
Payment Currency | USD | ||||
Exchange Rate | 0,00000000 | ||||
Payment Rate | 0,00000000 | ||||
Frequency Cat. | Periodic | ||||
Repeat. Period | 0 | ||||
1st Cal. Date | 01.01.2010 | ||||
Key Date | 0 | ||||
Frequency Cat. | Relative | ||||
Condition Group Type 2002 |
|||||
Create Condition | 101100 | ||||
Currency | USD | ||||
Valid From | 01.01.2010 | ||||
End Date | 31.12.2013 | ||||
Tab calculation |
|||||
Condition Form | |||||
Rounding Cat. | Round to the nearest | ||||
Interest Calc. Method | Act/365 | ||||
Rounding Unit | 0,0000000 | ||||
Interest Calc. | Straight-line | ||||
Amount | 0,00 | ||||
Percentage Rate | 3,00 | ||||
Pro Rate Calculation | Prorate calculation in shortened/extended per. | ||||
Base Amount | 0,00 | ||||
Base Reference | 0300 | ||||
Payment Currency | USD | ||||
Exchange Rate | 0,0000000 | ||||
Frequency Cal | Periodic | ||||
Repeat Period | 4 | ||||
1st Calc. Date | 01.01.2010 | ||||
Key Date | 0 | ||||
Frequency Cat. | Relative | ||||
PARTNER DATA |
|||||
Valid From | 01.01.2008 | ||||
Valid To | 31.12.9999 | ||||
Role | FS0040 | ||||
Name | issuer | ||||
ID Type | ID TP13 | ||||
Partner ID Number | 7879 | ||||
INSTRUMENT DATA | |||||
Instrument Type | SBOND | ||||
ISIN number | DE0987654366 | Own Issue | |||
Quotation | 01 | Percentage Quotation | Tradeble | Yes | |
Listing | Listed | ||||
Nominal Amount | 22,000.000.00 | USD | |||
Issue Amount | 27.000.000.00 | USD | |||
CREDIT EXPOSURE | |||||
Product Type | 430 | BOND | |||
Recognize Exchange | 1 | Yes | |||
FINANCIAL POSITION MANAGEMENT |
|||||
Accounting Standard | IAS | International Accounting Standard | |||
Generate FPO | 2 | Generate | |||
Financial Position Type | ODEBINST | Debt Instruments | |||
Component Class | M | Main Part | |||
Determination Acquisition Value | 1 | Not Residual | |||
Accounting Standard | HGB | German commercial code | |||
Generate FPO | 2 | Generate | |||
Financial Position Type | ODEBINST | Debt Instruments | |||
Component Class | M | Main Part | |||
Determination Acquisition Value | 1 | Not Residual | |||
KEY FIGURES |
|||||
AMOUNTS | |||||
Valid From | 01.01.2008 | ||||
Valid To | 31.12.2013 | ||||
Key Fig. Cat | Payoff amount | ||||
Amount | 20.000.000.00 | ||||
Currency | USD | ||||
BUSINESS TRANSACTION – eg. Bono | |||||
ENTRANCE SCREEN |
|||||
Business Transaction | LEXX BOND 2010 BT1 | ||||
Source System | MANUAL | ||||
Business Transaction Class | SBTS – Flow Trans. (Investment Prod.) | ||||
HEADER DATA |
|||||
Business Record Date | Automatically Filled | ||||
Posting Date | 01.01.2010 | ||||
Value Date | 01.01.2010 | ||||
CHARACTERISTICS |
|||||
Business Trams type | DI01 | ||||
Legal Entity | LEXX | Legal Entity | |||
ITEM CLASS | SIC9 | ||||
Item 001 | |||||
ITEM DATA | |||||
Account Category | 03 – Securities position Account | ||||
Account Number | Insert your settlement account | ||||
Template Category | 01 Financial Instrument | ||||
External Number | Insert your financial transaction | ||||
Nominal Amount | 22.000.000.00 | ||||
Nominal Currency | USD | ||||
Position Amount | 22.000.000.00 | ||||
Position Currency | USD | ||||
Transaction Amount | 22.000.000.00 | ||||
Transaction Currency | USD | ||||
CHARACTERISTICS |
|||||
Role in Sender/Receiver Relationship | N | Neutral | |||
Item Type | I00A | [P] Long-Term Receivables (Debit) |
You can verify and check master data and postings in the Result Data Layer via the SAP HANA Studio after the replication to SAP HANA. A technical expert, mentioned in chapter Roles, can carry out this activity.
Prerequisites
SAP HANA Studio must be installed on the client side to get access to the data.
Procedure
Choose Start All Programs SAP HANA Studio to open your SAP HANA Studio
In the navigator panel, expand your SAP HANA System Content SAP.fs. ba/sap.fs. find. ba and expand the respective Calculation Views / Analytic views folder or Attribute Views folder.
Right-click the respective view (for example CA_BALANCE) and choose Data Preview.
Verify that the replicated data are by filtering according to the relevant object.
Result
You have Master data and postings in the Result Data Layer are verified and checked in SAP HANA studio.
SAP HANA 1.0 December 2011 English
Building Block Configuration Guide Purpose
1) Preparation
2) Prerequisites
3) Configuration
3.1) Creation of Aggregated Data Table in SAP Bank Analyzer
3.2) Implementation of Rapid-Deployment Solution-Specific Programs (SAP Note 1614443) in SAP BANK Analyzer
3.3) SAP HANA – Data Model Overview
3.4) SAP HANA – Used Tables
3.5) SAP HANA – Use of Tables in Views
3.6) SAP HANA – Creating and Filling the REPORTING_STUCTURE Table
3.7) Balance Sheet Model Overview
3.8) Profit & Loss Model Overview
3.9) Sub ledger Models Overview
3.10) SAP Business Objects information Space Creation
4. Extension of Delivered Package and Associated Reporting Objects
4.1.1 Add Additional Attributes to Views in SAP HANA Package
4.1.2 Universe Enhancement
4.1.3 SAP Crystal Report Enhancement
Get In-Depth Knowledge
You liked the article?
Like: 0
Vote for difficulty
Current difficulty (Avg): Medium
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills in the market.